v6.0.0 #407
Merged
v6.0.0 #407
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Description Updates the URL Loader dependency to newest major release. ## Issue Ticket Number Fixes #<ISSUE_NUMBER> <!-- Specify above which issue this fixes by referencing the issue number (`#<ISSUE_NUMBER>`) or issue URL. --> <!-- Example: Fixes https://github.com/cloudinary-community/next-cloudinary/issues/<ISSUE_NUMBER> --> ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Fix or improve the documentation - [ ] This change requires a documentation update # Checklist <!-- These must all be followed and checked. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/cloudinary-community/next-cloudinary/issues) ticket for this PR - [ ] I have checked to ensure there aren't other open [Pull Requests](https://github.com/cloudinary-community/next-cloudinary/pulls) for the same update/change? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation BREAKING CHANGE: Updates URL Loader to new major version
# [6.0.0-beta.1](v5.18.0...v6.0.0-beta.1) (2024-01-16) ### Features * Updates URL Loader to 4.0 ([#406](#406)) ([26789ee](26789ee)) ### BREAKING CHANGES * Updates URL Loader to new major version
… with transformations deprecation
# [6.0.0-beta.2](v6.0.0-beta.1...v6.0.0-beta.2) (2024-01-16) ### Features * deprecating GetCldImageUrl and GetCldOgImageUrl types ([2e4f7e1](2e4f7e1)) * removing autoPlay prop (with capital p) in favor of autoplay ([393b2e1](393b2e1))
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
# Description The CldUploadWidget makes a request to an API endpoint when signing requests and currently doesn't pass along any headers such as Content-Type. This explicitly defines them as the payload as `application/json`. #379 ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Fix or improve the documentation - [ ] This change requires a documentation update # Checklist <!-- These must all be followed and checked. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/cloudinary-community/next-cloudinary/issues) ticket for this PR - [ ] I have checked to ensure there aren't other open [Pull Requests](https://github.com/cloudinary-community/next-cloudinary/pulls) for the same update/change? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation BREAKING CHANGE: CldUploadWidget signature endpoint now sets content-type as application/json
# [6.0.0-beta.4](v6.0.0-beta.3...v6.0.0-beta.4) (2024-01-19) ### Features * Add Content-Type to CldUploadWidget Signature Headers ([#418](#418)) ([4f86a20](4f86a20)) ### BREAKING CHANGES * CldUploadWidget signature endpoint now sets content-type as application/json
# Description Migrates the project to PNPM ## Issue Ticket Number Fixes #408 <!-- Specify above which issue this fixes by referencing the issue number (`#<ISSUE_NUMBER>`) or issue URL. --> <!-- Example: Fixes https://github.com/cloudinary-community/next-cloudinary/issues/<ISSUE_NUMBER> --> ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Fix or improve the documentation - [ ] This change requires a documentation update # Checklist <!-- These must all be followed and checked. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/cloudinary-community/next-cloudinary/issues) ticket for this PR - [ ] I have checked to ensure there aren't other open [Pull Requests](https://github.com/cloudinary-community/next-cloudinary/pulls) for the same update/change? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
# Description Adds publish branch configuration ## Issue Ticket Number Fixes #<ISSUE_NUMBER> <!-- Specify above which issue this fixes by referencing the issue number (`#<ISSUE_NUMBER>`) or issue URL. --> <!-- Example: Fixes https://github.com/cloudinary-community/next-cloudinary/issues/<ISSUE_NUMBER> --> ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Fix or improve the documentation - [ ] This change requires a documentation update # Checklist <!-- These must all be followed and checked. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/cloudinary-community/next-cloudinary/issues) ticket for this PR - [ ] I have checked to ensure there aren't other open [Pull Requests](https://github.com/cloudinary-community/next-cloudinary/pulls) for the same update/change? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
# [6.0.0-beta.6](v6.0.0-beta.5...v6.0.0-beta.6) (2024-01-19) ### Bug Fixes * Publish Branch ([#420](#420)) ([ababfb7](ababfb7))
# Description <!-- Include a summary of the change made and also list the dependencies that are required if any --> ## Issue Ticket Number Fixes #<ISSUE_NUMBER> <!-- Specify above which issue this fixes by referencing the issue number (`#<ISSUE_NUMBER>`) or issue URL. --> <!-- Example: Fixes https://github.com/cloudinary-community/next-cloudinary/issues/<ISSUE_NUMBER> --> ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Fix or improve the documentation - [ ] This change requires a documentation update # Checklist <!-- These must all be followed and checked. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/cloudinary-community/next-cloudinary/issues) ticket for this PR - [ ] I have checked to ensure there aren't other open [Pull Requests](https://github.com/cloudinary-community/next-cloudinary/pulls) for the same update/change? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
# [6.0.0-beta.7](v6.0.0-beta.6...v6.0.0-beta.7) (2024-01-24) ### Features * Manage Native Types from @cloudinary-util/types ([#421](#421)) ([fbb4608](fbb4608))
# Description * Updates the onError and onClose signatures to match other callback methods * Deprecates onUpload in favor of onSuccess, matching the native Cloudinary Upload Widget API
Updates homepage design
# [6.0.0-beta.15](v6.0.0-beta.14...v6.0.0-beta.15) (2024-02-23) ### Features * Homepage Updates ([#438](#438)) ([8958e52](8958e52))
# [6.0.0-beta.16](v6.0.0-beta.15...v6.0.0-beta.16) (2024-02-23) ### Features * CldOgImage fix, updating SEO in docs ([f8ce7e0](f8ce7e0))
Pulls in some config changes with inspiration from https://github.com/apollographql/apollo-client-nextjs/tree/main/packages/experimental-nextjs-app-support Trying a new way to import version numbers to hopefully fix type assertion errors
# [6.0.0-beta.17](v6.0.0-beta.16...v6.0.0-beta.17) (2024-02-24) ### Features * Fix Subpath Imports & Config ([#439](#439)) ([99786db](99786db))
# [6.0.0-beta.18](v6.0.0-beta.17...v6.0.0-beta.18) (2024-02-24) ### Features * attempting to fix package.json import ([993115d](993115d))
Wasn't able to get it working in a way that consistently worked between Pages and App Router. Will come back to it in a later version.
# [6.0.0-beta.19](v6.0.0-beta.18...v6.0.0-beta.19) (2024-02-24) ### Features * Revert Subpath Imports ([#440](#440)) ([b569709](b569709))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
CldImage, getCldImageUrl, CldOgImage, getCldOgImageUrl
CldImage
transformationsin favor ofnamedTransformationsgetCldImageUrl
CldUploadWidget
CldVideoPlayer
autoPlayin favor ofautoplayPost-Release TODO
Issue Ticket Number
Fixes #363
Fixes #379
Fixes #419
Fixes #327
Type of change
Checklist
BREAKING CHANGE: Updates URL Loader to new major version